Menlo Security

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index


Attribute Value
Connector ID MenloSecurityConnector
Publisher Menlo Security
Used in Solutions MenloSecurity
Collection Method Azure Function
Connector Definition Files MenloSecurity.json
Ingestion API Log Ingestion API | HTTP Data Collector API — Sibling ARM template declares DCR / Log Ingestion API resources; Connector definition requires workspace key (SharedKey pattern)

The Menlo Security connector uses the Menlo Security Logs API to ingest Audit, Bandwidth, and Web proxy logs into Microsoft Sentinel. It runs as three timer-triggered Azure Functions, each polling the API every 3 minutes and writing events to custom Log Analytics tables (MenloAudit_CL, MenloBandwidth_CL, MenloWeb_CL).

Tables Ingested

This connector ingests data into the following tables:

Table Transformations Ingestion API Lake-Only
MenloAudit_CL ? ✓ ?
MenloBandwidth_CL ? ✓ ?
MenloWeb_CL ? ✓ ?

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

1. Step 1 — Deploy the connector infrastructure

Click Deploy to Azure below. On the deployment page:

The template deploys the Function App, Key Vault, Storage Account, Data Collection Endpoint, and Data Collection Rule, and creates the MenloAudit_CL, MenloBandwidth_CL, and MenloWeb_CL custom tables in your Log Analytics workspace.

Deploy To Azure

To remove the connector later, delete the MenloSecurityLogs resource group and the three Menlo*_CL custom tables from the workspace.

2. Step 2 — Enable log collection

All log-collection functions are disabled by default. After deployment, navigate to the Function App in the Azure Portal and enable the log types you want to collect:

  1. Open the Function App created by this solution (named menlo-logs-func-<suffix>).
  2. Go to Configuration → Application settings.
  3. For each log type you want to enable, set the corresponding app setting value to 0:
Log type App setting name Enable value
Audit logs AzureWebJobs.TimerTriggerAuditLogs.Disabled 0
Bandwidth logs AzureWebJobs.TimerTriggerBandwidthLogs.Disabled 0
Web logs AzureWebJobs.TimerTriggerWebLogs.Disabled 0
  1. Click Save. Each enabled function will begin polling the Menlo Security API on a 3-minute interval.

3. Step 3 — Verify data ingestion

After enabling at least one log type, wait approximately 5–10 minutes for the first data to appear. Verify by running the following queries in Microsoft Sentinel Logs:

MenloAudit_CL | take 10
MenloBandwidth_CL | take 10
MenloWeb_CL | take 10

If no data appears after 15 minutes, check the Function App's Monitor tab for invocation errors.


Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index